-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PSCE-243 #53
PSCE-243 #53
Conversation
actions/trestle-bot/action.yml
Outdated
|
||
runs: | ||
using: "docker" | ||
image: "Dockerfile" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a path? Would it be different now that the action file is not in the root of the directory?
Related: PSCE-243 Signed-off-by: Alex Flom <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added some questions here about the overall approach.
- Consolidates multiple trestle-bot entrypoints within the published trestle-bot image. Related PSCE-243, PSCE-250 Signed-off-by: Alex Flom <[email protected]>
@@ -81,7 +81,7 @@ outputs: | |||
|
|||
runs: | |||
using: "docker" | |||
image: "Dockerfile" | |||
image: "quay.io/continuouscompliance/trestlebot:latest" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we point to the pre-built image, I would prefer we not point to latest. Pointing to latest means that older versions of the trestlebot action could be pointing to the newest image and breaking changes could make older version of the action unusable (i.e. inputs are expected, but not provided in the action.yml)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this approach. Do you think we could transform the autofix.sh
to python? Maybe on another PR? It would be really useful in #55 if I could reuse some of that logic.
'twas cherry-picked. Closing |
No description provided.